Skip to content

Bump CI actions to Node 24 majors to clear runner deprecation warning - #18

Merged
lgamorim merged 1 commit into
masterfrom
feature/ci-node24-actions
Aug 13, 2026
Merged

Bump CI actions to Node 24 majors to clear runner deprecation warning#18
lgamorim merged 1 commit into
masterfrom
feature/ci-node24-actions

Conversation

@lgamorim

Copy link
Copy Markdown
Owner

@

Why

GitHub Actions runners have deprecated Node 20 and annotate every run that uses a node20-based action (changelog). ci.yml used actions/checkout@v4, actions/setup-dotnet@v4, and actions/upload-artifact@v4, all of which run on Node 20.

What

Bump each action in ci.yml to its current major, all running on Node 24:

  • actions/checkout v4 → v7 — Node 24 since v5; v6 persists credentials to a separate file and v7 blocks fork-PR checkout for pull_request_target/workflow_run triggers, neither of which affects this workflow.
  • actions/setup-dotnet v4 → v6 — Node 24 since v5; v5.4 validates that global.json has a fully-qualified sdk.version when rollForward is set, which ours (10.0.301) satisfies. v6 is an internal ESM migration.
  • actions/upload-artifact v4 → v7 — defaults to Node 24 since v6; v7 adds an optional archive input. The name/path inputs used here are unchanged.

No inputs or behavior used by this workflow changed across these majors.

docs.yml and release.yml still reference the v4 actions (and docs.yml also uses node20-based upload-pages-artifact@v3); left out of scope to keep this change focused.

🤖 Generated with Claude Code
@

GitHub Actions runners deprecated Node 20 and annotate every run that
uses a node20 action. checkout v4, setup-dotnet v4, and upload-artifact
v4 all run on node20, so bump each to its current major:

- actions/checkout v4 -> v7 (Node 24 since v5; v6/v7 changes do not
  affect this workflow's usage)
- actions/setup-dotnet v4 -> v6 (Node 24 since v5; global.json's
  fully-qualified sdk.version satisfies the stricter v5.4 validation)
- actions/upload-artifact v4 -> v7 (Node 24 default since v6; the
  name/path inputs used here are unchanged)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@lgamorim
lgamorim force-pushed the feature/ci-node24-actions branch from acaa8bc to 16440e4 Compare August 13, 2026 14:46
@lgamorim
lgamorim merged commit 121d52e into master Aug 13, 2026
8 checks passed
@lgamorim
lgamorim deleted the feature/ci-node24-actions branch August 13, 2026 14:59
@lgamorim lgamorim added this to the Phase 6 — Ship (1.0.x) milestone Aug 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant